Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1600

reference
496-tree-1
name
1600
tree-preservation-order

undefined

496-tpo-1
uprn
address-text
point
POINT (-1.036763 50.886750)
geometry
MULTIPOLYGON (((-1.036707 50.886744,-1.036709 50.886755,-1.036717 50.886765,-1.036729 50.886773,-1.036745 50.886778,-1.036763 50.886780,-1.036780 50.886779,-1.036796 50.886774,-1.036809 50.886766,-1.036817 50.886756,-1.036820 50.886745,-1.036818 50.886734,-1.036810 50.886723,-1.036797 50.886715,-1.036782 50.886710,-1.036764 50.886708,-1.036747 50.886710,-1.036731 50.886715,-1.036718 50.886723,-1.036710 50.886733,-1.036707 50.886744)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL